Simultaneous Multi-Mode WiFi Differentiated By SSID

ABSTRACT

Embodiments provide a wireless network with several access points connected to a communication infrastructure. Residential or business customers of the Internet are provided an Internet interface (e.g., a digital subscriber line (DSL) modem) having a wireless transceiver. Two or more users may access the Internet or other network through the Internet interface. Each user can be assigned a unique Service Set-Identifier (SSID) with each SSID associated with a type of service (e.g., user video service, backhaul service, etc.). The amount of bandwidth assigned to the type of service (and user) may be governed by the equipment according to the assigned SSID.

BACKGROUND

Many municipalities or organizations are attempting to create wirelessnetworks throughout the city or town. The wireless network would allowcitizens, residents, workers, etc., to connect to the Internet or othernetwork from any location within the city or town. As such, people caninterface for business or other reasons easily regardless of location.

To create the wireless networks, a first wireless access point isconnected to the Internet. The connection is the gateway from thewireless network to the communications infrastructure (e.g. the phonecompany telecommunications network). From the first wireless accesspoint, one or more other wireless access points are created thatcommunicate with the first wireless access point. The other wirelessaccess points share the bandwidth provided by the first wireless accesspoint. More wireless access points may be connected further downstreamand divide the bandwidth further. As can be seen, the more wirelessaccess points built the further the bandwidth must be divided. Thenetwork access points become untenable at some point as the bandwidthcannot be divided further without diminishing the network's ability toprovide service. Therefore, the wireless networks are limited in thearea the networks can span and cannot grow or expand beyond a certainnumber of access points without imposing serious performancelimitations. The limited access points can affect the quality of serviceprovided to the user.

It is in view of these and other considerations not mentioned hereinthat the embodiments of the present disclosure were envisioned.

BRIEF SUMMARY

Embodiments presented in this application provide a wireless networkwith several access points connected to the communicationinfrastructure. In embodiments, residential or business customers of theInternet are provided an Internet interface (e.g., a digital subscriberline (DSL) modem) having a wireless transceiver. Two or more users mayaccess the Internet or other network through the Internet interface.

Each user can be assigned a unique Service Set-Identifier (SSID). Theuser's access to the Internet interface is predicated on the SSID. Infurther embodiments, each SSID may represent a type of service. Forexample, the resident who owns the equipment may be assigned one or moreSSIDs for phone service, data service, video or television service, etc.An SSID may be assigned to a backhaul service that allows another remotewireless access point to connect to the Internet through the equipment.Further, the amount of bandwidth assigned to the type of service may begoverned by the equipment and assigned to each SSID as appropriate.

This Summary is provided to introduce some embodiments. The Summary isnot meant to limit the claims in any manner or form—the possibleembodiments are defined by the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the present disclosure are described in conjunctionwith the appended figures:

FIGS. 1A and 1B are block diagrams of embodiments of wireless networks;

FIG. 2 is a block diagram of an embodiment of DSL/Wireless Access Pointequipment;

FIG. 3 is a block diagram of an embodiment of software and/or hardwarecomponents executable by the DSL/Wireless Access Point equipment;

FIG. 4 is a block diagram of an embodiment of a data structure for adata packet transmitted through or by the wireless network;

FIG. 5 is a flow diagram of an embodiment of a method for providingbandwidth to different types of service in a wireless network;

FIG. 6 is a flow diagram of an embodiment of allocating bandwidth todifferent types of service;

FIG. 7 is a block diagram of an embodiment of a computer system operablein the wireless network; and

FIG. 8 is a block diagram of an embodiment of a network.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

DETAILED DESCRIPTION

The ensuing description provides exemplary embodiment(s) only and is notintended to limit the scope, applicability or configuration of thepossible embodiments. Rather, the ensuing description of the exemplaryembodiment(s) will provide those skilled in the art with an enablingdescription for implementing an exemplary embodiment. It beingunderstood that various changes may be made in the function andarrangement of elements without departing from the spirit and scope ofthe possible embodiments as set forth in the appended claims.

Embodiments of the present disclosure provide a unique and novelwireless network. The wireless network may be used to provide service toa municipality or other area. A home or business user can provide apoint of presence (POP) for a wireless network to a communicationinfrastructure. For example, a user may install an Internet modem intotheir residence to provide Internet access. In embodiments, theequipment the user installs includes a wireless access point and anInternet interface. The Internet interface can be a DSL modem, a cablemodem, or other communications device that can communicate over anetwork that accesses the Internet.

The wireless access point can provide service to both the local userthat owns or leases the equipment but also provide a POP to one or moreother users. For example, another user may be sitting at a park benchoutside the residence and access the internet through the wirelessaccess point. In alternative embodiments, the wireless access point canallow direct access by other users or provide access to one or moreother wireless access points that use a backhaul function in theequipment. Users may include, but are not limited to, people accessingthe system with a personal computer, other wireless access points, orwireless access points further downstream from the equipment.

To manage the different users and bandwidth, each type of service may beassigned a unique SSID. The SSID may be used by the equipment to limitthe bandwidth or assign bandwidth to one or more user depending on whothe user is or for what the user needs the service. In otherembodiments, the SSID may be used to establish priorities for providingQuality of Service (QoS) parameters. For example, a user that owns theequipment and pays subscriber fees may have a first SSID associated witha private class of service. Another user accessing the Internet from anarea outside the residence or business may have a second SSID associatedwith a public class of service. One or more wireless access points usinga backhaul feature may have third or other SSIDs. Each type of servicemay receive a predetermined amount of bandwidth. For example, theresident with the first SSID may have the largest amount of bandwidth,while the other users may receive a portion of the remaining bandwidth.

While various aspects of embodiments of the disclosure have beensummarized above, the following detailed description illustratesexemplary embodiments in further detail to enable one of skill in theart to practice the disclosure. In the following description, for thepurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the present disclosure. Itwill be apparent, however, to one skilled in the art that the presentdisclosure may be practiced without some of these specific details. Inother instances, well-known structures and devices are shown in blockdiagram form. Several embodiments of the disclosure are described below,and while various features are ascribed to different embodiments, itshould be appreciated that the features described with respect to oneembodiment may be incorporated with another embodiment as well. By thesame token, however, no single feature or features of any describedembodiment should be considered essential to the disclosure, as otherembodiments of the disclosure may omit such features.

An embodiment of a system 100 for providing a wireless network is shownin FIG. 1A and FIG. 1B. In embodiments, the system 100 includesequipment 104 resident in or in proximity to a user's residence(residence 2), business, or other user facility or building 102. Theequipment 104 may be purchased, leased, or used by the user (user 1) 105as agreed in a service contract. For example, user 1 105 agrees toreceive Internet access from a company (e.g., Qwest or another internetservice provider). User 1 105 then receives the equipment 104 as part ofthe agreed service. In embodiments, user 1 105 can access the Internetthrough the equipment either by a wired or wireless connection as shownin FIG. 1.

In embodiments, the equipment 104 includes a wireless access point andan Internet interface. The interface to the Internet may be a modem,router, or other device for establishing communication with a network106 over connection 120. The network 106 can be a communicationsnetwork, for example, a phone company system, or other network thatforms a portion of the Internet (e.g., the World Wide Web). Inembodiments, the network 106 is the same as the Internet. Thus, a userinterfacing with the equipment may be able to send information to andreceive information from one or more websites over the Internet. In anembodiment, the Internet interface is a DSL modem, a cable modem, amicrowave transceiver, a phone modem, a satellite transceiver, a router,or other device. Hereinafter, the Internet interface will be describedas a DSL device. However, one skilled in the art will recognize that theInternet interface may be other devices, all of which may communicatethrough a network interfacing with or forming a portion of the Internet.

The equipment 104 provides a wireless access point for one or more otherusers (also referred to as clients). The wireless access point inequipment 104 can be any hardware and/or software operable to providewireless communications for one or more computers. For example, thewireless access point is a transceiver operable to communicate usingcommunication standard 802.11g, Bluetooth, or other wireless standard orprotocol. Referring to FIG. 1B, the users or clients may belong to oneor more user classes based on the type of user service offered,connection characteristics, bandwidth requirements, quality of servicecharacteristics, type of data being downloaded or uploaded, or by one ormore other distinctions. In an embodiment, clients may be separated intotwo classes—either private or public clients. Private clients are usersthat may have a contract with the ISP and are provided a secure andestablished amount of bandwidth. The private clients may include anyuser in a family or organization covered by the ISP contract. In otherembodiments, the private clients are associated with the private WiFinetwork provided by equipment 104 and in communication with the Internetinterface 104. Public clients may be clients that use the wirelessnetwork to access the Internet but do not have a contract with the ISP.Public clients can be given bandwidth as available, and the connection(being through a publicly accessible link) may not be secure or assecure as a private client's connection. In alternative embodiments, apublic client is not associated with the private WiFi network providedby equipment 104.

Private clients may be further divided into subcategories depending onthe type of user service provided. A private client can use the privateclient connection to access the Internet or for data (e.g., email), todownload video or multimedia content, to make phone calls using VoIP, orfor one or more other services. A first private client 124 is using abest-effort data service. A second private client 122 is using a voiceservice, and a third private client 120 is using a video service. Oneskilled in the art will recognize further types of user service that maybe included. Further, private clients (clients contracting with the ISP)may access a wireless network associated with the ISP that is in adifferent location from their facility. In these situations, the privateclient is considered a roaming client. For example, a first roamingclient 128 is using a best-effort data service through WAP 108, which isdifferent from the client's normal access point. A second roaming client132 may be using a voice service.

Public clients may also be further divided like private clients. Thus, afirst public client is using a best-effort data service and a secondpublic client is using a voice service. Some public clients may also bepreferred. For example, police, fire rescue, public works, or othergovernmental agencies may receive preferred access as public clients.Further, public clients may also include access by a businessequivalent. A business equivalent may be a user that has reciprocitywith the ISP from a contract with another ISP.

Referring back to FIG. 1A, user 1 105 in residence 2 102 may be aprivate client and user 119 in residence 116 may be a roaming privateclient or a public client depending on if user 2 contracted with theISP. User 2 119 may not have the equipment 104 to access the Internetbut may have a contract with the same ISP and still be a private client.The contract with the ISP allows user 2 119 to access the Internetthrough one or more other user's equipment 104. In other embodiments,user 2 119 pays for the service per usage and does not have a contractwith the ISP, and thus, is considered a public client. User 2 may accessthe equipment 104 through a wireless access point 118 that communicateswith the wireless access point in the equipment 104. User 3 may be aroaming client or a public client.

The wireless network system 100 may include one or more other wirelessaccess points, such as, wireless access points 108 and 112. Wirelessaccess points 108 and/or 112 may be located outside any residence andprovide wireless access to public clients or to private clientscontracted with the ISP. In embodiments, the other wireless accesspoints 108 and/or 112 include any hardware and/or software tocommunicate with the wireless access point in the equipment 104 andallow access by another user, such as user 3 109. The wireless accesspoint 108 is in communication with the equipment 104 through wirelessconnection 110.

In embodiments, wireless access point 112 is in communication withwireless access point 108 through another wireless connection 114. Thus,wireless access point 112 communicates with the equipment 104 throughwireless access point 108. A network of wireless access points can becreated using the equipment 104 as a root node. However, one or moreother residences can also include equipment 104 that functions as a rootnode. Thus, the wireless network is serviced not by a single or a fewroot nodes but by many root nodes within several residences orbusinesses. This configuration allows for larger bandwidth allocationsand better service.

The system 100 may also include an ISP server 107 that is incommunication with the equipment 104 through the network 106. The ISPserver 107 can change settings or install new software or information tothe equipment 104. Further, the ISP server 107 may communicate throughthe WAP 104 to the other WAPs 108 and 112. Thus, the ISP server 107 canmanage the wireless network through the WAP 104. In embodiments, anyconnection shown in FIG. 1A or other figures may be wired, wireless, ora combination of wired and wireless connections, regardless of whetherthe connection is represented by a line or lightning bolt. Theseconnections may be Bluetooth, 802.11b, wired LAN, or other typeconnection.

One or more embodiments of the equipment 200 are shown in FIG. 2. Inembodiments, equipment 200, hereinafter referred to as a NID/WAP, is thesame or similar to equipment 104 described in conjunction with FIG. 1.The NID/WAP 200 can include, but is not limited to, a network interfacedevice (NID) (e.g., a NID 202), a wireless access point (WAP) 204, and acommunication bus 206. The NID 202 is hardware, software, or hardwareand software for communicating with a network 208, which is a portion ofor is in communication with the Internet. The NID 202 may be a DSL modembut the DSL modem is only one possible communication device that may beused in the NID/WAP 200. In other embodiments, the NID 202 is replacedwith a cable modem that communicates with a cable network attached tothe Internet, a satellite receiver and/or transceiver in communicationwith a satellite network that is attached to the Internet, etc. The NID202 can communicate with a phone company network or other communicationnetwork or system and transmit data to and receive data from theInternet. The phone company (for example, Qwest) may function as theISP. In embodiments, all communications to and from the Internet arecommunicated through the NID 202.

The WAP 204 is the hardware, software, or hardware and software forcommunicating wirelessly with one or more users. In embodiments, the WAP204 is a wireless transceiver. The WAP 204 can communicate in a wirelessstandard, e.g., 802.11g, Bluetooth, etc. The WAP 204 communicates withone or more other wireless systems. For example, the WAP 204communicates with laptop 212 over a wireless communications link. TheWAP 204 can communicate with one or more other components, such as theNID 202, over a communication bus 206.

The communication bus 206, in embodiments, is a wired bus having one ormore connection points for one or more components. The communication bus206 provides a communication facility for the WAP 204 to communicatedata to the NID 202. A user computer 210 can also be directly connectedto the communication bus 206 that can transmit data to the NID 202.Thus, the communication bus 206 provides communication to and from theNID 202.

The WAP 204 can communicate with one or more other wireless accesspoints. In embodiments, the bridge mode allows one or more WAPs toprovide a backhaul service. For example, the WAP 204 communicates withWAP 214 and WAP 216 in a bridge mode. More or fewer WAPs may communicatewith WAP 204 as represented by ellipses 218. In the bridge mode, the WAP204 provides a link for WAP 214 and WAP 216 to access the Internetthrough NID 202. In embodiments, the bridge mode allows one or more WAPsto use a backhaul service. In operation, WAP 214 and WAP 216 communicatedata to WAP 204. WAP 204 communicates the data over the communicationbus 206 to NID 202, which transmits the data to network 208. Inembodiments, the NID 202 receives data from the network 208 and sendsthe data to WAP 204 over the communication bus 206. WAP 204 sends thedata to either of WAP 214 and WAP 216 over a wireless link.

In embodiments, the NID/WAP 200 includes a digital signal processor(DSP) device 220. The DSP device 220 can provide investigation,modification, cancellation, and creation of data within one or more datapackets sent between WAP 204 and the NID 202. In embodiments, the DSPdevice 220 inspects packets communicating between the WAP 204 and theNID 202. The DSP device 220 can assist the WAP 204 and/or the NID 202organize and manage communications within the NID/WAP 200. Inembodiments, the functions performed by the DSP device 220 may beincorporated into the WAP 204 and/or the NID 202.

An embodiment of software components 300 operable to managecommunications in the NID/WAP is shown in FIG. 3. The softwarecomponents 300 may execute in the DSP device 220 (FIG. 2), the NID 202(FIG. 2), the WAP 204 (FIG. 2), or a combination of the DSP device 220(FIG. 2), the WAP 204 (FIG. 2), and/or the NID 202 (FIG. 2). Thesoftware components 300 may include, but are not limited to, a packetinspection component 304, an assignment engine 306, a networkcommunication component 308, a priority engine 312, and/or an allocationengine 314.

In embodiments, the software components 300 manage the severalconnections through the WAP 204 (FIG. 2) and through the NID 202 (FIG.2). The NID 202 can have a limited or set amount of bandwidth totransmit data to the network 208 (FIG. 2). As such, the softwarecomponents 300 manage which user is assigned which type of connection. Atype of connection may be governed by how much bandwidth is allocatedthrough the NID 202 (FIG. 2) or what quality of service (QoS) parametersare managed. QoS parameters may include jitter, latency, droppedpackets, bytes, or bits, out-of-order-delivery, error rates, delay, etc.To achieve a predetermined level of QoS parameters, the connection mayrequire more or less bandwidth. In embodiments, the type of QoSparameters is determined by the type of data being communicated. Forexample, delay or latency would make voice calls difficult, andtherefore, the latency or delay for VoIP service would be good. Incontrast, video service may not have as great a need for high latencymetrics but may need very low dropped packets because dropped packetscould cause pixilation of a video playback. Other types of data servicewould need other types of QoS settings, as one skilled in the art willrecognize.

To identify the class of user, connection type, QoS parameters, type ofuser service, etc., the software components 300 can use the SSID. Inembodiments, the software components 300 assign or determine the SSIDand associate the SSID with a class of user or a type of service. Forexample, the private client (e.g., residential user) 210 (FIG. 2) mayhave a first SSID that is associated with a first type of service, e.g.,best-effort data service. The WAP 214 can have a second SSID associatedwith a second type of service, e.g., backhaul service.

The packet inspection component 304 determines the SSID associated withan incoming/outgoing data packet 302. In embodiments, the data packets302 may be incoming if the data packets are received from the network208 (FIG. 2) and are bound for a user. The data packet 310 is outgoingif the data packet is from a user and bound for the network 208. Thepacket inspection component can perform deep packet inspection todetermine the SSID.

In alternative embodiments, one or more of the software components shownin FIG. 3 are part of the ISP server 107 (FIG. 1A). For example, the ISPserver 107 (FIG. 1A) can include the priority engine 312, the database316, and/or the allocation engine 314. The ISP server 107 (FIG. 1A) mayalso share some or all the functionality of these components with theWAP. The ISP server 107 (FIG. 1A), having the priority engine 312, thedatabase 316, and/or the allocation engine 314, can manage theallocation of bandwidth or provision of QoS parameters remotely. Forexample, the ISP server 107 (FIG. 1A) determines that all privateclients should have the highest priority over the public clients or theroaming clients. As such, the priority engine 312 sets the priority, andthe allocation engine 314 establishes rules for allocating the bandwidthaccording to the priority. The priority and allocation rules may besaved in the database 316. Then, when needed, the WAPs using the ISP canretrieve the rules. In other embodiments, the ISP server 107 (FIG. 1A)pushes the established rules to the WAPs using the ISP. With centralcontrol, the ISP server 107 (FIG. 1A) can manage the entire network andchange rules as needed. For example, if the government passes a law thatpolice, fire, medical organizations should have unfettered access to thewireless network, the ISP server 107 (FIG. 1A) can simply change therules giving these public clients the highest priority and push therules to the WAPs in the network. This ability eliminates the need toreconfigure separately every WAP, and the need to make the changeon-site.

An embodiment of a data packet 400 is shown in FIG. 4. Data packet 400can be similar to or the same as data packet 302 (FIG. 3). The datapacket 400 can have a header 402 and a data portion 404. The header 402can include the SSID 406 and one or more other items of headerinformation 408. The packet inspection component 304 (FIG. 3) candetermine the location of the header 402 in a data packet 400. In otherembodiments, the packet inspection component 304 (FIG. 3) determines anew data packet 400 is being received and can determine the firstportion of the data packet 400 which includes the header 402.

Upon determining the header 402, the packet inspection component 304(FIG. 3) can locate and read the SSID 406 from the header 402. Inembodiments, the packet inspection component 304 (FIG. 3) sends the SSID406 to the assignment engine 306 (FIG. 3). The SSID 406 may be sentcontemporaneously or substantially at the same time as the data packet302 (FIG. 3) is sent to the assignment engine 306 (FIG. 3).

In an alternative embodiment, the SSID is only assigned to the datapackets according to the class of user. The packet inspection component304 determines the type of service by conducting deep packet inspectionand inspecting the data included in the data portion 404 of the datapacket 400. For example, an email message may have certain datacharacteristics that identify the data packet 400 as an email message.The packet inspection component 304 can inspect the data packet 400 forthe email message characteristics. Upon finding the characteristics, thepacket inspection component 304 sends a message indicating the datapacket 400 is associated with a best-effort data service. Similardeterminations can be made for VoIP, video, audio, multimedia, and othertypes of service.

In still other embodiments, the SSID can identify different private orpublic access rights. The SSID can identify the security to be appliedto data sent over the wireless network. For example, a user can haveprivate access protected with a wireless security method (WiredEquivalency Privacy (WEP), Wi-Fi Protected Access (WPA), WPA2, strictauthentication of devices under 802.1X or 802.11i, etc.). A useraccessing the network using a different SSID may use a public networkwithout security or little security applied to the data transmissions.Thus, a resident owning the equipment may have a private network whileusers using another WAP in bridge mode may have public access rights.

The priority engine 312 (FIG. 3) can determine which user has the higherpriority to service. In embodiments, each SSID has an associatedpriority that reflects the priority of the type of service. An exampleof a priority scheme is shown in Table 1 below:

TABLE 1 Exemplary Priority Scheme Type of SSID User Service Priority 1Private Client (Residential User) VoIP 1 2 Roaming Client (WirelessAccess Point 1 - Best-Effort 2 Contract User) 3 Wireless Access Point 2Backhaul 3 4 Public Client (Wireless Access Point 3 - Video 4Non-contract User)

The first SSID (SSID 1) is assigned to the residential user, which maybe the laptop 212 (FIG. 2) or the in-residence computer 210 (FIG. 2)associated with the owner of the equipment. The residential user is aprivate client. This user is the primary user of the bandwidth.Therefore, the residential user may have the highest priority to anybandwidth or QoS parameters. The second SSID (SSID 2) may be associatedwith a user, who is not the residential user, but who has a servicecontract with the ISP. Thus, this contract user may have the secondpriority. In embodiments, the third SSID (SSID 3) is associated with awireless access point (e.g., WAP 214 (FIG. 2)) that has a backhaulconnection through WAP 204 (FIG. 2). Since WAP 214 (FIG. 2) may havecontract users accessing the Internet through the WAP 214 (FIG. 2), theWireless Access Point 2 may have the third priority. Finally, anon-contract user may be assigned SSID 4 and have the lowest priority. Anon-contract user is a user that does not have a service contract withthe ISP but is using the WAP 204 (FIG. 2) for a one-time or infrequentconnection. Table 1 provides only an example of possible priorities andone skilled in the art will recognize other types of service and otherpriority schemes.

Returning to FIG. 3, an allocation engine 314 can allocate bandwidth orother service parameters to each type of service. For example, theresidential user may have a minimum bandwidth requirement, for example,4.0 Mbps. In embodiments, the remaining bandwidth may be allocated amongthe other users. For example, a contract user may receive 3 Mbps while anon-contract user may receive 1 Mbps. The allocation may also may bedynamic. Thus, the residential user may receive all the bandwidth theuser requires. Any remaining bandwidth may be allocated to the otheruser according to the priority of the user. Thus, if the second priorityuser is allocated all of the remaining bandwidth, the third priorityuser would not receive any bandwidth.

The allocation engine 314 may also allocate bandwidth among two or morevirtual private networks (VPNs). Rather that managing separateconnections on the same network, the allocation engine 314 can generatetwo or more VPNs. Each type of user may have one of the VPNs assigned.As such, the user interacts over a network having a separate set ofproperties, including the amount of bandwidth available.

The assignment engine 306 can assign bandwidth or a VPN to each of theusers. In embodiments, the assignment engine 306 receives the SSID fromthe packet inspection component 304. If the SSID has been assigned anallocation of bandwidth, the amount of assigned bandwidth will be shownin a data structure in the database 316. The assignment engine 306 canretrieve the information from the database and enforce the amount ofbandwidth assigned. If no allocation of bandwidth has been assigned, theassignment engine 306 can create a new record in the database 316. Then,the priority engine 312 and the allocation engine 314 can set priorityand an allocation of bandwidth for the user. The priority and allocationmay be stored in the database 316.

As the assignment engine 306 receives data packets from the packetinspection component 304, the assignment engine 306 ensures that theuser is provided the correct service. Thus, the assignment engine 306may interface with the priority engine 312 and/or the allocation engine314 to provide the correct quality of service. In embodiments, theassignment engine 306 receives information about priority or allocationdirectly from the priority engine 312 and/or the allocation engine 314.In other embodiments, the priority engine 312 and/or the allocationengine 314 stores the priority and/or allocation information in thedatabase 316. The assignment engine 306 then retrieves the informationfrom the database 316. The assignment engine 306 may receive theinformation after receiving or assigning the SSID. In subsequenttransmissions from and/or to the user with the SSID, the assignmentengine 306 need not retrieve the information again.

The assignment engine 306 can send the assignment information, the VPNor bandwidth allocation for the SSID, to the network communicationcomponent 308. In embodiments, the networking component 308 is thehardware, software, or hardware and software for the wireless connection(similar to wireless connection 110 (FIG. 1)). In other embodiments, thenetworking component 308 is the hardware, software, or hardware andsoftware for the network 106 (FIG. 1). Thus, the system 300 can controlthe multi-mode connections in the DSL communication processor 202, theDSP device 220, and/or the wireless communication component 204.

The network communication component 308 can receive packets from theassignment component 306. The network communication component 308 cancontrol the bandwidth provided a user by communicating the allowedbandwidth to the user. In other embodiments, the network communicationcomponent 308 rejects packets above the threshold for the allowedbandwidth. In still other embodiments, the network communicationcomponent 308 queues packets that are over the bandwidth and sends thepackets. Regardless, the network communication component 308 controlsthe amount of bandwidth provided to each user.

An embodiment of a method 500 for providing a point of presence for awireless network is shown in FIG. 5. In embodiments, the method 500generally begins with a START operation 502 and terminates with an ENDoperation 514. The steps shown in the method 500 may be executed in acomputer system as a set of computer executable instructions. While alogical order is shown in FIG. 5, the steps shown or described can, insome circumstances, be executed in a different order than presentedherein. The method 500 will hereinafter be explained with reference toFIGS. 1-4.

A wireless access point 104 receives an incoming wireless data packet instep 504. The wireless data packet may be received from another wirelessaccess point 108. In embodiments, one or more hardware components (e.g.,antennae, transceiver, etc.) receives the wireless data packet. Thewireless data packet may then be forwarded to the packet inspectioncomponent 304. The packet inspection component 304 receives the wirelessdata packet for the wireless access point 104.

The wireless access data packet is inspected by the packet inspectioncomponent 304 to determine the SSID associated with the data packet instep 506. In embodiments, the packet inspection component 304 scans theheader 402 for the SSID 406. The packet inspection component 304 canthen read the SSID 406 from the header information 402.

The network communications component 308 receives the data packet andprovides the appropriate bandwidth associated with the SSID in step 508.To provide the appropriate bandwidth, the assignment engine 306 mayreceive the data packet and the SSID from the packet inspectioncomponent 304. The assignment engine 306 searches the database 316 forinformation about the SSID. Upon finding the SSID, the assignment engine306 can assign an amount of bandwidth to the SSID. The assignment engine306 may base the amount of bandwidth on the priority assigned the SSIDby the priority engine 312. The priority for the SSID can be a functionof the type of data or service associated with the SSID. For example, ifthe type of data or service is internet backhaul service for a wirelessaccess point 108, then the SSID will be assigned a lower priority than adata packet from the user 105 that owns the wireless access equipment104.

In embodiments, an allocation engine 314 may determine how to divide thebandwidth. For example, the allocation engine may provide a set 6 Mbpsto the user 105 and then provide only 2 Mbps to the user 109 connectedthrough the wireless access point 108 using the backhaul to the WAP 104.In other embodiments, the amount of bandwidth allocation is dynamic. Theallocation engine 314 provides the user 105 with as much bandwidth asnecessary. The other services may split the remaining bandwidth asnecessary. A priority list may be used to determine the amount ofbandwidth for the remaining users. As such, a second higher priorityuser may receive as much bandwidth as required and then each user begiven bandwidth as needed until no bandwidth remains. Some users withthe lowest priorities may not receive any bandwidth in somecircumstances.

The information about the priority or allocation is provided to theassignment engine 306. The assignment engine 306 provides the assignmentof the bandwidth to the network communication component 308 that limitsthe bandwidth for the data packet. The network communication component308 may then send the data packet through the WAP to the DSL modem instep 510. The NID 202 can receive the data packet and transfer the datathrough the NID 202 to the network 106 in step 512.

In embodiments, a similar procedure can occur for data downloaded to auser through the WAP 104. Data may be received at the WAP 204 from theNID 202. The packet inspection component 304 can determine the SSID. Theassignment engine 306 can assign a certain amount of bandwidth for theWAP 204 according to an allocation for the SSID. The WAP 204 may thensend the data to a user having a set bandwidth. In other embodiments,the amount of bandwidth associated with an SSID is the sum of both theupload and the download rates.

An embodiment of a method 600 for providing a point of presence for awireless network is shown in FIG. 6. In embodiments, the method 600generally begins with a START operation 602 and terminates with an ENDoperation 614. The steps shown in the method 600 may be executed in acomputer system as a set of computer executable instructions. While alogical order is shown in FIG. 6, the steps shown or described can, insome circumstances, be executed in a different order than presentedherein. The method 600 will hereinafter be explained with reference toFIGS. 1-4.

The NID/WAP equipment 200 can determine the type of service in step 604.The type of service can include, but is not limited to, residentcustomer service, customer wireless access, backhaul service, backhaulservice for non-customers, etc. Each type of service can be identifiedbased on various characteristics. For example, the type of service canbe based on the customer being serviced (customer with an account,customer that owns the local equipment, non-customer, etc.), the type ofaccess (local wireless, backhaul, etc.), the type of information beinguploaded or downloaded (e.g., video download, audio download, email,etc.), or other characteristics. In embodiments, the ISP or controllerof the network 106 interfaces with the NID/WAP equipment 200 toestablish the types of service categories and characteristics.

The priorities for the different types of service are determined in step606. In embodiments, the ISP or controller of the network 106establishes the priorities for the different types of services. Thepriorities can be based on operational or business concerns. Forexample, backhaul service may be rated a higher priority that wirelessaccess for a non-customer in some circumstances. The ISP or controllerof the network 106 may remotely interface with the NID/WAP equipment 200to establish the types of service and the priorities.

The ISP or controller of the network 106 can establish a system toallocate bandwidth to the various types of service depending on thepriority in step 608. In embodiments, the ISP or controller of thenetwork 106 remotely interfaces with the NID/WAP equipment 200 to setbandwidths for the different types of service. For example, the localcustomer may receive 8 Mbps out of a total 12 Mbps. A backhaul servicemay receive 3 Mbps. In other embodiments, the ISP or controller of thenetwork 106 may establish a rule to allocate bandwidth. For example, therules may allow the local customer to user as much bandwidth as neededfor an action and then allow the next highest priority type of serviceto use as much bandwidth as needed. The amount of bandwidth needed maybe measured by the speed of an incoming or outgoing signal. As such, thebandwidth allocation ensures that the local interface is not abottleneck for the customer. Other methods for allocating the bandwidthare possible and contemplated.

Each type of service may be given an SSID, and each SSID may beassociated with the type of service in step 610. For example, theNID/WAP equipment 200 can generate an SSID for each user using each typeof service. Each user using a certain type of service can have theirassigned SSID associated with the type of service. The NID/WAP equipment200 stores the SSID allocation in a database 316.

In embodiments, band width is initially limited by the SSID, but may befurther limited by the particular service if multiple services aresupported by the SSID. The amount of bandwidth allowed for any user canbe limited according to the SSID in step 612. The NID/WAP equipment 200can also determine the amount of bandwidth for each type of service.Each user with an SSID associated with a particular type of service canthen have the bandwidth allocated limited according to SSID and/or thetype of service requested by the user. In embodiments, the amount ofbandwidth allocated for two or more users using the same type of servicecan also be determined. For example, a first user may be allocated morebandwidth than a second user even if both users are using the same typeof service. The NID/WAP equipment 200 stores the allocations for eachSSID in a database 316 for retrieval and can complete packet inspectionto determine the type of service requested.

FIG. 7 provides a generic schematic illustration of a structure of adevice 700 that may be used to implement all or a portion of the NID/WAP104, user computer 105, WAP 108, or one or more other systems orcomponents described herein. Those skilled in the art will appreciatethat various modifications and/or customizations of the device 700 maybe appropriate, depending on the role of the device 700 in variousembodiments. Hence, FIG. 7 should be understood to illustrate broadlyhow individual device elements may be implemented in a relativelyseparated or relatively more integrated manner. The device 700 is showncomprised of hardware elements that are electrically coupled via bus702, including a processor 704, an input device 706, an output device708, one or more storage device(s) 710, and a memory 714. The computersystem may also include a computer-readable storage media reader thatmay be further connected to a computer-readable storage medium, thecombination comprehensively representing remote, local, fixed, and/orremovable storage devices plus storage media for temporarily and/or morepermanently containing computer-readable information. The communicationssubsystem 712 may comprise a wired, wireless, modem, and/or other typeof interfacing connection and may permit data to be exchanged with thevarious other system components.

The device 700 may also comprise software elements, shown as beingcurrently located within working memory 714, including an operatingsystem 716 and other code 718, such as one or more application programsdesigned to implement methods of the invention. It will be apparent tothose skilled in the art that substantial variations may be made inaccordance with specific requirements. For example, customized hardwaremight also be used and/or particular elements might be implemented inhardware, software (including portable software, such as applets), orboth. Further, connection to other computing devices such as networkinput/output devices may be employed.

Several exemplary embodiments of the invention will be described indetail. For instance, FIG. 8 illustrates a schematic diagram of a system800 that can be used in accordance with one set of embodiments. Thesystem 800 can include one or more user devices 805 a, 805 b, and 805 c,which, purely for illustrative purposes, are shown on FIG. 8 as a userdesktop computer 805 a, a user desktop computer 805 b, and a laptopcomputer 805 c. The user devices 805 a, 805 b, and 805 c can compriseany device capable of data and/or voice communication. Exemplary userdevices can include general purpose personal computers (e.g., 805 a)(including, merely by way of example, personal computers and/or laptopcomputers running any appropriate flavor of Microsoft Corp.'s Windows™and/or Apple Corp.'s Macintosh™ operating systems) and/or workstationcomputers running any of a variety of commercially-available UNIX-r orUNIX-like operating systems. Alternatively, the user devices 805 a, 805b, and 805 c can be any other electronic device, such as a thin-clientcomputer, POTS telephone, wireless telephone, Internet-enabled mobiletelephone, handheld computer and/or personal digital assistant, capableof voice and/or data communication, including merely by way of examplecommunication via a computer network and/or displaying and navigatingweb pages or other types of electronic documents. These user devices 805a, 805 b, and 805 c, depending on their capabilities, can also have anyof a variety of applications, including one or more database clientand/or server applications, and/or web browser applications. Althoughthe exemplary system 800 is shown with three user devices, any number ofuser computers can be supported.

Certain embodiments of the invention operate in a networked environment,including a network 810. The network 810 can be any type of networkfamiliar to those skilled in the art that can support datacommunications using any of a variety of commercially-availableprotocols, including without limitation TCP/IP, SNA, IPX, AppleTalk™,and the like. Merely by way of example, the network 810 can be a localarea network (“LAN”) including without limitation an Ethernet network, aToken-Ring network and/or the like; a wide-area network; a virtualnetwork, including without limitation a virtual private network (“VPN”);the Internet; an intranet; an extranet; a telephone network, includingwithout limitation a public switched telephone network (“PSTN”), awireless telephone network, a private branch exchange (“PBX”) and/or thelike; an infra-red network; a wireless network, including withoutlimitation a network operating under any of the IEEE 802.11 suite ofprotocols, the Bluetooth™ protocol known in the art, and/or any otherwireless protocol; and/or any combination of these and/or othernetworks.

Embodiments of the invention can include one or more server computers815 a and/or 815 b which can serve as processing systems in accordancewith certain embodiments of the invention. Merely by way of example, aserver 815 a and/or 815 b may be a web server, which can be used toprocess requests for web pages or other electronic documents from userdevices 805 a. 805 b, and 805 c. The servers 815 a and 815 b each can berunning an operating system, including without limitation any of thosediscussed above, as well as any commercially-available server operatingsystems, including, merely by way of example, OS/390™, OS/400™, VMS™,UNIX™ (including any of its varieties and/or similar variants), and thelike. The servers 815 a and 815 b can also run a variety of serverapplications, including HTTP servers, FTP servers, CGI servers, databaseservers, Java servers, and the like.

Servers 815 a and 815 b can also include one or more file servers,application servers and/or transaction processing servers, which can, inaddition to an operating system, include one or more applicationsaccessible by a client running on one or more of the client devices 805a, 805 b, and 805 c. Merely by way of example, the server(s) 815 aand/or 815 b can be one or more general purpose computers capable ofexecuting programs or scripts in response to requests from and/orinteraction with the user devices 805 a, 805 b, and 805 c, includingwithout limitation web applications. Such web applications can beimplemented as one or more scripts or programs written in anyprogramming language, such as Java™, C, or C++, or any scriptinglanguage, such as Perl, Python, or TCL, or any combination thereof. Theservers 815 a and 815 b can also include database servers, includingwithout limitation those commercially available from Oracle™,Microsoft™, Sybase™, IBM™ and the like, which can process requests fromdatabase clients running on a user device. In some embodiments, one ormore servers 815 a and 815 b can create web pages dynamically forperforming methods of the invention. These web pages can serve as aninterface between the user devices 805 a, 805 b, and 805 c and theservers 815 a and 815 b. Alternatively, a server 815 a and 815 b may runa server application, while a user device (e.g., 805 a, 805 b, and 805c) can run a dedicated client application. The server application,therefore, can serve as an interface for the user device running theclient application.

In some implementations, a server 815 a and/or 815 b may include atelephone interface, which can allow the server to interact with anordinary (POTS) telephone. The telephone interface, which may beimplemented in software and/or hardware embodied in the server 815 a,815 b, and/or in a separate device in communication with the server, canprovide integrated voice response (“IVR”) features familiar to thoseskilled in the art. The telephone interface also can be configured tointerpret dual tone multi-frequency (commonly known as “DTMF” or“Touchtone®”) tones as data input. Thus, in accordance with embodimentsof the invention, the telephone interface can allow for a user tointeract with a server 815 a and 815 b via voice and/or DTMF commands.

In certain embodiments, the system can include a database 820 a and/or820 b. The location of the database 820 a and/or 820 b is discretionary:the database 820 a and/or 820 b can reside on a storage medium local to(and/or resident in) one or more of the computers and/or user devices805 a, 805 b. 805 c, 815 a and 815 b. Alternatively, the database 820 aand/or 820 b can be remote from any or all of the computers 805 a, 805b, 805 c, 815 a and 815 b, so long as the database 820 a and/or 820 bare in communication (e.g., via the network 810) with one or more ofthese. In a particular set of embodiments, the database 820 a and/or 820b can reside in a storage-area network (“SAN”) familiar to those skilledin the art. (Likewise, any necessary files for performing the functionsattributed to the devices and/or computers 805 a. 805 b. 805 c, 815 aand 815 b can be stored locally on the respective computer and/orremotely, as appropriate.) In an embodiment, the database 820 a and/or820 b can be a relational database, that is adapted to store, update,and retrieve data in response to SQL-formatted commands.

While the invention has been described with respect to exemplaryembodiments, one skilled in the art will recognize that numerousmodifications are possible. For example, the methods and processesdescribed herein may be implemented using hardware components, softwarecomponents, and/or any combination thereof. Further, while variousmethods and processes described herein may be described with respect toparticular structural and/or functional components for ease ofdescription, methods of the invention are not limited to any particularstructural and/or functional architecture but instead can be implementedon any suitable hardware, firmware and/or software configuration.Similarly, while various functionality is ascribed to certain systemcomponents, unless the context dictates otherwise, this functionalitycan be distributed among various other system components in accordancewith different embodiments of the invention.

Moreover, while the procedures comprised in the methods and processesdescribed herein are described in a particular order for ease ofdescription, unless the context dictates otherwise, various proceduresmay be reordered, added, and/or omitted in accordance with variousembodiments of the invention. Moreover, the procedures described withrespect to one method or process may be incorporated within otherdescribed methods or processes; likewise, system components describedaccording to a particular structural architecture and/or with respect toone system may be organized in alternative structural architecturesand/or incorporated within other described systems. Hence, while variousembodiments are described with—or without—certain features for ease ofdescription and to illustrate exemplary features, the various componentsand/or features described herein with respect to a particular embodimentcan be substituted, added and/or subtracted from among other describedembodiments, unless the context dictates otherwise. Consequently,although the invention has been described with respect to exemplaryembodiments, it will be appreciated that the invention is intended tocover all modifications and equivalents within the scope of thefollowing claims.

Also, it is noted that the embodiments may be described as a processwhich is depicted as a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart may describethe operations as a sequential process, many of the operations can beperformed in parallel or concurrently. In addition, the order of theoperations may be re-arranged. A process is terminated when itsoperations are completed, but could have additional steps not includedin the figure. A process may correspond to a method, a function, aprocedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination corresponds to a return of the functionto the calling function or the main function.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks may be stored in a machine-readable medium such as a storagemedium. A processor(s) may perform the necessary tasks. A code segmentmay represent a procedure, a function, a subprogram, a program, aroutine, a subroutine, a module, an object, a software package, a class,or any combination of instructions, data structures, or programstatements. A code segment may be coupled to another code segment or ahardware circuit by passing and/or receiving information, data,arguments, parameters, or memory contents. Information, arguments,parameters, data, etc., may be passed, forwarded, or transmitted via anysuitable means including memory sharing, message passing, token passing,network transmission, etc.

In light of the above description, a number of advantages of the presentdisclosure are readily apparent. For example, the in-residence WAP canallow for access from various other WAPs. Due to the abundance of thein-residence WAPs, a municipal wireless network can be created withseveral POPs. This configuration improves access and the bandwidthallocation of previous networks. Further, the embodiments presented canprovide a customizable allocation of bandwidth based on the type ofservice. Thus, the in-residence user can be provided sufficientbandwidth while allocating other bandwidth to other users.

While the principles of the disclosure have been described above inconnection with specific apparatuses and methods, it is to be clearlyunderstood that this description is made only by way of example and notas limitation on the scope of the disclosure.

What is claimed:
 1. A wireless access point for use in a multi-modewireless network, the wireless access point comprising: a wirelessaccess point component, the wireless access point component wirelesslycommunicating with a second wireless access point and a third wirelessaccess point, wherein the second wireless access point is associatedwith a first SSID and provided a first portion of bandwidth by thewireless access point component based on the first SSID, and wherein thethird wireless access point is associated with a second SSID andprovided a second portion of bandwidth by the wireless access pointcomponent based on the second SSID; and a NID in communication with thewireless access point component, the NID receiving first data from anetwork and sending the first data to the second wireless access pointand receiving second data from the third wireless access point andsending the second data to the network.
 2. The wireless access point asdefined in claim 1, the first wireless access point further comprising aDSP device for evaluating one or more data packets communicated betweenthe wireless access point component and the NID.
 3. The wireless accesspoint as defined in claim 1, wherein the second wireless access point isin communication with a first user associated with a first class ofuser, wherein the wireless access point component provides the firstportion of bandwidth based on the class of user.
 4. The wireless accesspoint as defined in claim 1, wherein the wireless access pointcomprises: a packet inspection component, the packet inspectioncomponent operable to inspect received data packet for the first SSID orthe second SSID; a priority engine, the priority engine operable todetermine a priority for assigning bandwidth to the second wirelessaccess point and the third wireless access point, wherein the priorityengine operable to also assign bandwidth to a first class of user and asecond class of user accessing the second wireless access point; anallocation engine, the allocation engine operable to allocate the firstportion of bandwidth and the second portion of bandwidth based on thepriority; a database, the database operable to store the priority andthe allocation; a network communication component, the networkcommunication component operable to provide the first portion ofbandwidth and the second portion of bandwidth; and an assignment enginein communication with the packet inspection component, the priorityengine, the allocation engine, the database, and the networkcommunication component, the assignment engine operable to receive thedata packet and SSID associated with the data packet from the packetinspection component, retrieve the allocation of bandwidth associatedwith the SSID from the database, and instruct the network communicationcomponent to provide the amount of allocated bandwidth for the datapacket.
 5. The wireless access point as defined in claim 4, wherein thepriority is based on a type of service associated with the secondwireless access point.